fix: close extension lifecycle release gaps#54
Merged
Conversation
- Delete generated investigation, plan, and review docs artifacts.\n- Remove stale release evidence references to deleted investigation notes.\n\nCo-authored-by: Codex <noreply@openai.com>
- propagate cookie and browser-mode options through macro CLI, daemon, and tool surfaces - tighten extension, daemon, provider fallback, and social/search classification behavior - add regression coverage for signed-in provider, Best Buy product-video, and daemon stop paths Co-authored-by: Codex <noreply@openai.com>
- isolate secondary matrix and direct provider daemon ownership from dirty relay clients - fail closed when configured daemon recycling cannot stop the previous daemon - expand direct provider and workflow matrix coverage for signed-in extension lanes Co-authored-by: Codex <noreply@openai.com>
- add the validation campaign plan across commands, tools, modes, and planes - record provider, Best Buy, secondary matrix, tool-family, and daemon lifecycle evidence - preserve follow-up classifications with current verification notes Co-authored-by: Codex <noreply@openai.com>
- close dependent relay clients when extension sockets drop - make ops client disconnect and daemon lifecycle cleanup fail closed - reject unsupported serve --daemon before it can start a foreground daemon Co-authored-by: Codex <noreply@openai.com>
- await fallback cleanup and disconnect failures within bounded budgets - preserve extension start URLs and retry semantics for signed-in provider fallback - cover community, shopping, and cleanup contamination paths Co-authored-by: Codex <noreply@openai.com>
- require clean owned relay state before signed-in provider runs - recycle configured daemons only after verified stop outcomes - avoid dirty relay and shell-owned daemon contamination in matrix/probe paths Co-authored-by: Codex <noreply@openai.com>
- document stale daemon and shell-owned foreground daemon findings - record fixed secondary matrix and provider contamination outcomes - update real-world surface validation plan status Co-authored-by: Codex <noreply@openai.com>
- align root package, lockfile, and extension manifest metadata - prepare tag-driven GitHub and npm release workflow for v0.0.29 Co-authored-by: Codex <noreply@openai.com>
Update first-run and CLI package artifact examples for the 0.0.29 release version. Co-authored-by: Codex <noreply@openai.com>
- keep reconnect suppression visible even when native transport remains connected - fail closed on required provider fallback cleanup and tighten daemon stop cleanup - cover relay dirty-state, ops cleanup, popup status, and fallback cleanup regressions Co-authored-by: Codex <noreply@openai.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Testing
Release note